Ham Radio 2000 #1

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 #1 / Ham Radio 2000.iso / ham2000 / hf / dsp / pac016 / docs < prev next >

Wrap

Text File | 1993-12-03 | 17.6 KB | 522 lines

PC-PACTOR V0.16 PC-PACTOR (c) Johan Forrer KC7WW 1992,1993,1994 Author: Johan B. Forrer KC7WW 26553 Priceview Drive Monroe, OR 97456 United States of America CIS id: 70730,3472 Shareware notice This program is distributed as a Shareware product. You may freely copy and share the program with your friends, associates and other radio amateurs. PC-PACTOR may not be sold or distributed with another product without the express written permission of the author. The author, Johan Forrer, KC7WW will only support unmodified copies of this software. If you decide to use this product, you should become a registered user by sending $5.00 or equivalent in foreign currency together with the completed registration form to the author. All transactions must be drawn on US banks. Upon receipt of your registration, you will receive one free update disk containing the latest release of the software . You will also be notified of future developments. Improvements are continually being made and exciting additions are under way or in the process of being implemented. If you are not satisfied with the program after registering it, you have 30 days from your registration date to return it for a full refund of your money, no questions asked. Previously registered users may obtain a free upgrade to this version - please send a formatted disk and SASE (or stamped mailer or 2 IRC's). This program may not be used by business or government institutions without proper licensing. Acknowledgements PACTOR is the development of H-P Helfert, DL6MAA, and U. Strate, DF4KV, and the WAA group. Hans-Peter generously provided the necessary details on the PACTOR implementation with the understanding that its sole purpose be for amateur usage. The assistance of Dr. Thomas Rink, DL2FAK is gratefully acknowledged. Please support the efforts of shareware developers. Table of contents 0.0 Quick summary for this release. 1.0 PC-PACTOR what does it do ? 1.1 Minimum requirements to run PC-PACTOR 1.2 CAUTION 1.3 Planned enhancements 2.0 Introduction 3.0 Hardware Interface 4.0 Installation 4.1 Software 5.0 Operating PC-PACTOR 5.1 Function keys 5.2 Command menu 6.0 Appendix 6.1 If problems persist..... 6.2 A few notes about HF modems. 7.0 Disclaimer 0.0 Quick summary for Version 0.16 Welcome to this is experimental version of PC-PACTOR. Any version number below 1.00 is considered experimental. Version 0.16 will receive and decode, 100 or 200 baud operation, ascii or Huffman compressed text and will allow the transmission of FEC mode or so called "unproto" mode. The user can thus monitor traffic, as well as transmit check-summed data frames. The full ARQ version still under development. For users familiar with PCTOR, the following guidelines will help: 1. Set your computer to run at least 8 Mhz. a 286/386/486 computer is preferable. 2. Ensure that your modem will pass 200 baud modulation. 3. Ensure that you have optimized the "TIMING" factor for your computer using PCTOR. Note down the factor that you use for later entry in PC-PACTOR. The timing adjustment is required each time PC-PACTOR is restarted. Timing is a little more critical than for AMTOR due to the longer packets. 4. Copy both PACTOR.EXE and CODE.DAT to your disk. 5. Start PC-PACTOR. It will go into MONITOR mode. 6. What can you expect to see? With strong signals on a quiet band, you will see error-free copy. On variable conditions there will be the occasional loss of print due errors within the received packet. These gaps in the traffic will show as ≈≈. It is educational to watch the lower status line. 7. If you hit F1, PC-PACTOR will enter the FEC mode and text entered via the keyboard will be sent over the air. Note that at this time, only ascii text will be transmitted. Ascii data files may also be transmitted using ALT-F menu. An FEC transmission is ended with F4. This way, any data remaining in the keyboard buffer will first be sent before the MONITOR mode is entered. However, F10 remains the "panic button" - it will terminate any transmitting operation. 8. A startup configuration file has been added. This allows the user to customize PC-PACTOR. 9. The user can optionally log all traffic to a disk file for later analysis. Time stamps will be inserted into the log file at regular intervals.1.0 PC-PACTOR what does it do ? Using only a low cost external HF modem, PC-PACTOR makes it possible to decode PACTOR on PC compatible hardware without the need of dedicated multi-mode terminal node controller (TNC) hardware. All decoding is performed in software in real time using only PC hardware. PC-PACTOR implements the most challenging and essential parts of the PACTOR protocol, ie. decoding at both 100 and 200 baud simultaneously, CRC calculation, and Huffman decompression. Since most users devote more time printing PACTOR traffic, this was considered the main priority. 1.1 Minimum requirements to run PC-PACTOR PCTOR will run on an IBM PC or close compatible computer with a clock speed at least 8 Mhz. DOS 3.1 or higher is required. A monochrome or EGA/VGA display adaptor will work. Although the software will run on a floppy-based system, a hard disk is recommended. The definition of "true IBM compatibility" is fuzzy and a great deal of flexibility has been built into the programs to handle a wide range of PC hardware. The program has been tested on a PC-clone with a 8 Mhz V20 chip, as well as a 486/33. A machine with at least a 10 Mhz clock is recommended. An HF modem capable of decoding 200 baud FSK is required to decode received audio to +/- 12V RS232 logic signals (please see 6.2 for further notes on HF modems). The actual polarity corresponding to the mark signal is not important for PACTOR, since the protocol uses both normal and inverted bits. PCTOR uses some of the signal lines of COM 1 as a digital interface. Presently only COM 1 is supported.1.2 Caution This software may not be suitable for all working environments. The user should therefore proceed with the usual caution and make sure critical software is backed up. Every effort has been made to ensure that the software is "well behaved", however, the user is reminded that this software relies on critical timing. Normal system functionality is retained, i.e. time-of-day and floppy disk timeout activities. The user must thus be careful not to run other software that relies on similar "tricks" that PC-PACTOR uses as the consequences is indeterminable. Normal program usage and program termination will undo the actions of PC-PACTOR and restore normal system operation. Should a program failure occur, the only way to restore normal system operation is to reboot DOS. 1.3 Planned enhancements Several enhancements are planned for release in the near future. As a registered user you will be notified of these when it becomes available. These include: * Full transmit/receive with memory ARQ support. This requires a special type of modem as the software needs to sample signals within the modem. Without this capability, true memory ARQ is not possible, regardless of what you may have been told. * PC-PACTOR/PCTOR Integration. This will provide a common user- interface for all digital modes of operation, make it possible to sync on either PACTOR or AMTOR automatically. 2.0 Introduction PC-PCTOR is an implementation of PACTOR as developed by the WAA group: DF4KV, DL6MAA, DL3FCJ, DL2FAK, DL1ZAM, DK5FH, and DF4WC. PACTOR uses adaptive speed, ISO 3309 CRC of data blocks, and allows on-the-fly Huffman data compression. Automatic error repeat (ARQ) as well as "unprotected" (UNPROTO) mode of transmission is used. PC-PCTOR contain a user-interface program that works in conjunction with several low-level routines that enables a user to operate and monitor PACTOR traffic with a minimum of fuss. Its multiple-window user interface allows simultaneous monitoring of decoded traffic, decoding status, and user keyboard history. Pop- up windows is used for setting operational parameters. PC-PCTOR was developed using Borland C++ Version 3.1. The low- level interface was developed using Borland Turbo Assembler version 3.0. 3.0 Hardware interface PC-PACTOR interfaces through signals of COM1 RS232 port. The following allocation of RS232 signals have been made: Other signal pins may be connected, however will play no part in the operation of PC-PACTOR. Note that for a minimal interface, DTR, RTS, DCD, and Ground, is required. For a 25-pin serial connector: pin 20 (DTR) - output data bits (mark -12V, space +12V) pin 4 (RTS) - PTT (off -12V, on +12V) pin 8 (DCD) - input data bits (mark -12V, space +12V) pin 7 (Ground) For a 9-pin serial connector: pin 4 (DTR) - output data bits (mark -12V, space +12V) pin 7 (RTS) - PTT (off -12V, on +12V) pin 1 (DCD) - input data bits (mark -12V, space +12V) pin 5 (Ground) 4.0 Installation 4.1 Software It is assumed that a hard disk is available, though the program can be run off a floppy disk as well. In fact it is suggested that you first run off a floppy disk to see if this software is compatible with other software that you may have on your system. 1. Create a new subdirectory and change directory to it, i.e. mkdir pactor cd pactor 2. Copy the contents of the floppy to the new subdirectory. copy a:*.* The following files will be copied: pactor.exe -- The split screen AMTOR program. code.dat -- Contains the WAA-supplied Huffman dictionary pactor.doc -- This documentation. pactor.cnf -- An example configuration file 3. Customize pactor.cnf (see 4.2 Customizing the configuration) Note that the device driver ANSI.SYS should be in your config.sys (please see about ANSI.SYS in your DOS manual).4.2 Customizing the configuration To enable a user to streamline the setup of the program to his requirements, a configuration file, "pactor.cnf" is read during startup. Read and edit the contents of the provided file "pactor.cnf" to suit your own preferences. This file is optional, but when not found, the system will use defaults. These entries are all optional, and may appear in any order, however, please do not enter any spaces between symbols, i.e. vid : 1 is NOT the same as vid:1 (The last one is correct). The following entries may be customized: id:KC7WW ----- set your identity selcal/callsign txdelay:25 ----- delay (ms) after PTT on till data out.This gives your transmitter time to changeover to transmit. timing:25 ----- system clock timing adjustment log:1 ----- receive data capture (logging) logfile:pctor.log ----- data capture filename vid:1 ----- DIRECT video I/O enabled (see appendix on hardware compatibility) fcrlf:1 ----- Files, i.e. buffers and files to be sent through the ALT-F command should use the AUTOMATIC CR/LF mode. This means that all CR's in the input text files will be ignored, and LF will be interpreted as CR/LF. refr:15 ----- Status update rate. The number of system ticks between updates, i.e. 15*55mS=0.825 seconds. To fast a rate will flicker or perhaps may introduce timing problems, too slow will affect animation of timing bar, clock, etc. time:0 ----- Use local time in displays and logging. If UTC time is required, use time:1 (also refer to the TZ environment variable). word:1 ----- Turns word-edit mode on. 5.0 Operating PCTOR Upon startup, the shareware banner will be displayed. Press the ESC key to proceed to the PC-PACTOR screen. The contents and layout of the status display line depends on which options the user has selected. The following description refers to the case when all the options are enabled. This gives the reader a description of all possibilities. PC-PACTOR displays two windows: the upper status line and the received traffic window. The upper status line is updated in real time and some machines may show some flickering. This is normal. The present operating state is displayed on the left of this status line, i.e. STANDBY or MONITOR. Decoder status information is displayed on the second, lower upper status line. This includes: HI, LO - 200 baud, 100 baud respectively. +, - - The bit sense of the received packet: - inverted, + normal ASCII, HUFFMAN - Ascii or Huffman data. Cnt - Received packet counter (0-3). Sync - The received sync character (in hexadecimal). Decoding third party PACTOR traffic, means that there is no means for correcting errors within received packets. For this reason the packet count is monitored for breaks in sequence. If a sequence break is encountered, the symbol ≈≈ is printed to show the gap. 5.1 Function keys The function keys have the following functions: F1 - Initiate a FEC ("unproto") transmission; F4 - Initiate QRT sequence (revert to standby condition). F6 - Initiate MONITOR (listen) mode. F10 - Abort any operation in progress and revert to standby mode. ESC - Calls up the command menu. ALT-R - Enter the remote station's callsign (eight chars max) ALT-F - Enter the files menu. For transmitting data files.5.2 Command Menu The command menu (called up when the ESC key is pressed when in the main display) has the following one letter commands: H - Help with the function keys. Q - Terminate PC-PACTOR. T - Set clock timing. This parameter allows fine adjustments of the master clock. See Appendix A for more details. V - Toggles video mode (DIRECT/BIOS). X - Exit the command menu to main display. The ESC key may also be used for this purpose. Y - Sends out a 500 HZ pulse train from pin 20 for diagnostic purposes. 6.0 APPENDIX. 6.1 If problems persists....... The most common feedback from users appears to be setting up PC- PACTOR's master clock timing. The clock timing is adjusted using the "T" option in the command menu. Adjust it a tick or two at a time, each time exiting the command menu and monitoring traffic. Once this "magic" number has been determined, note it down for later use.6.2 A few notes on HF modems Experience have shown that some modems perform better than others. We may divide the class of popular modems roughly into three categories (there are a few other types as well): (I) The phase locked loop (PLL), (II) filter type, (III) digital signal processing (DSP) type. It is the author's opinion that the PLL type of modems are not suitable for average HF operations. It is best to avoid this approach even with extensive front-end filtering. The filter-type modem have been used with much greater success on HF. However, there are various kinds of approaches in filter-type modems: Vintage designs like the ST-5 and ST-6 employed L/C filters and are known to work reasonably well, given that some changes are made to their low-pass filters (mainly to pass the 200 Hz PacTOR modulation rate). Active filter designs such as the DJ6HP will also work quite well under fair conditions, however, do not expect too much under adverse conditions. Another popular active filter modem is the BARTG design. This small modem will work reasonably well too, however it lacks front-end bandpass filtering, and has poor post- discriminator signal processing. Both these designs are good for newcomers. Modern good performance filter-type modems use sophisticated front end filters in conjunction with well-designed discriminators and extensive post discriminator filtering circuitry. They generally have excellent dynamic range to handle strong signals as well as being able to "dig into the noise" to handle weaker signals. They will tolerate some degree of off- frequency operation. It also has become popular to monitor analog levels of signals within the modem in order to implement "soft" error correction techniques. Although this does not necessarily mean an increase the level of hardware sophistication, additional interfacing and software support is required. The DSP approach is still new to HF operation, yet holds a lot of promise. There are presently some commercial units available. Please contact the author about details for a low cost HF digital DSP modem. 7.0 Disclaimer The author, Johan Forrer KC7WW is not responsible for any damage, injury, loss of profit or gain associated with the use, installation, or application of this software. January 1993 J.B.Forrer KC7WW 26553 Priceview Drive Monroe, OR 97456 United States of America